-
Notifications
You must be signed in to change notification settings - Fork 5.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
br/operator: fix adapt env for snapshot backup stuck when encountered error #52607
br/operator: fix adapt env for snapshot backup stuck when encountered error #52607
Conversation
Signed-off-by: hillium <yu745514916@live.com>
Hi @YuJuncen. Thanks for your PR. PRs from untrusted users cannot be marked as trusted with I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #52607 +/- ##
=================================================
- Coverage 74.3558% 58.1086% -16.2472%
=================================================
Files 1470 1602 +132
Lines 354521 621964 +267443
=================================================
+ Hits 263607 361415 +97808
- Misses 71638 236908 +165270
- Partials 19276 23641 +4365
Flags with carried forward coverage won't be shown. Click here to find out more.
|
Signed-off-by: hillium <yu745514916@live.com>
Signed-off-by: hillium <yujuncen@pingcap.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rest lgtm.
Co-authored-by: BornChanger <97348524+BornChanger@users.noreply.github.com>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: BornChanger, Leavrth The full list of commands accepted by this bot can be found here. The pull request process is described here |
[LGTM Timeline notifier]Timeline:
|
In response to a cherrypick label: new pull request created to branch |
In response to a cherrypick label: new pull request created to branch |
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
… error (pingcap#52607) (pingcap#52969) (pingcap#88) close pingcap#52846 Co-authored-by: Ti Chi Robot <ti-community-prow-bot@tidb.io>
/run-cherry-picker |
In response to a cherrypick label: new pull request created to branch |
In response to a cherrypick label: new pull request created to branch |
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
What problem does this PR solve?
Issue Number: close #52049
Problem Summary:
When we failed to prepare the connections for wait apply, the channel may never be closed. Hence the pause PD operation (which relies on the finishing of the prepare connections stage) get stuck.
What changed and how does it work?
Selected over the context so it can be canceled.
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.